There are still deprecation warnings for glide. As it it beyond our control I guess we'll have to accept it. But is it really necessary to rebuild the stylesheets for glide? The npm package contains pre-built stylesheets, why are we not using them?

When I test to import the pre-built css-files I get the same output in style.css except that some classes have color #fff instead of white which both are white. Also I find no place where the imported scss aliases (glideCore and glideTheme) are used in our scss files. So in my opinion we could change the use statement in scss/externs/glidejs/import.scss to import the pre built css-files instead. But I'm no expert in stylesheets, so even I wouldn't trust me.

There is an issue logged for this in the glide repo: glidejs/glide#704

The glide stuff aside, this PR does not produce the same CSS as before. Basically all definitions have lost a top level selector, either .o-ui for ui-elements or .o-map for everything else. Here are two examples. but it looks the same for all definitions. Not sure if it affects anything as the selection is only widened. Maybe if map is embedded in a document that has more content than just the app wrapper. Also possibly the print control seems to search for exact style definitions const h4Rule = getCssRule('.o-ui h4, .o-ui .h4'); to resize them.

Before:

.o-ui .rounded {
  border-radius: 0.25rem;
  overflow: hidden;
}

After:

.rounded {
  border-radius: 0.25rem;
  overflow: hidden;
}

Before:

.o-map svg,
.o-map object {
  width: 100%;
}

After:

svg,
object {
  width: 100%;
}

Seems to be a effect of switching from @import to @use that the scope is lost. I'll try to get it back some how.

Do I have to edit every scss file and add the scope to all that had it before or are I'm missing something?

I surely am no export in CSS nor SASS, but from the looks of it, it is only the SASS @import extension that is deprecated, which means that the CSS @import statement is still valid inside a rule. My guess is that you start off by having a @use at the top and leave the @import inside o-map, possibly renaming all @use namespaces.

See example at https://sass-lang.com/documentation/at-rules/use/, look at the 'Loading Members' example.

Have you tried the SASS migrator?

Now it produces correct stylesheet, had to use correct syntax for the nested imports.
The glide warnings remains though.

Had to move import order to avoid a warning to last, so comment moved.